Release 10.1A: OpenEdge Development:
Debugging and Troubleshooting

Deleted objects

There are cases where the application deletes an object with a DELETE OBJECT statement, but OpenEdge delays the deletion of the object. One example is an output TABLE-HANDLE parameter. If the 4GL application deletes this object before returning, OpenEdge delays the deletion so it can transfer the output temp-table records back to the calling program when the program returns. If OpenEdge delays the object deletion, a log entry indicates that the deletion is pending. A log entry also indicates when OpenEdge deletes the object. This can happen with the following object types:

BUFFER (associated with an output TABLE-HANDLE parameter).
DATASET (for example, an OUTPUT DATASET-HANDLE parameter).
PROCEDURE (for example, if a procedure contains DELETE THIS-PROCEDURE).
TEMP-TABLE (for example, an OUTPUT TABLE-HANDLE parameter).